Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1753

reference: 480-tree-1
name: 1753
tree-preservation-order: undefined
480-tpo-1
uprn
address-text
point: POINT (-1.022787 50.884699)
geometry: MULTIPOLYGON (((-1.022730 50.884693,-1.022732 50.884704,-1.022740 50.884714,-1.022753 50.884722,-1.022768 50.884727,-1.022786 50.884729,-1.022804 50.884728,-1.022819 50.884723,-1.022832 50.884715,-1.022841 50.884705,-1.022844 50.884694,-1.022841 50.884683,-1.022833 50.884673,-1.022821 50.884665,-1.022805 50.884659,-1.022787 50.884657,-1.022770 50.884659,-1.022754 50.884664,-1.022741 50.884672,-1.022733 50.884682,-1.022730 50.884693)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL